Improve sorting and displaying algorithms for top-clients and top-domains #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your PR:
Please submit all pull requests against the
development
branch. Failure to do so will delay or deny your requestHow familiar are you with the codebase?:
10
getTopDomains()
. Instead of assuming how many lines of data we have sent, we can also explicitly count them.getTopClients()
. As a by-product this also adds the optionaldesc
feature to the top clients requests where it wasn't available before.Note that I completely removed the
skip
variable as it is not important how many lines we have already skipped when now directly count the number of returned datasets.The new code has been tested against two possible failures:
Both tests returned the expected results.
This template was created based on the work of
udemy-dl
.